-
Notifications
You must be signed in to change notification settings - Fork 50
Allow region-ized fields in OpenStack CloudProfileConfig #482
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but I wanted to do some testing next week.
/cc @gardener/dashboard-maintainers - PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice PR! I have a general comment about the setting override, though.
For the keyStoneURL
the non region specific setting overrides the region specifics and for LoadBalancerProvider
and FloatingPool
the order of elements determines how it is overwritten. I think this should be a) consistently handled and b) the region specifics should overrule the non-region specifics. WDYT?
controllers/provider-openstack/pkg/apis/openstack/validation/cloudprofile.go
Show resolved
Hide resolved
controllers/provider-openstack/pkg/controller/controlplane/valuesprovider.go
Outdated
Show resolved
Hide resolved
controllers/provider-openstack/pkg/controller/controlplane/valuesprovider.go
Outdated
Show resolved
Hide resolved
controllers/provider-openstack/pkg/controller/worker/machines.go
Outdated
Show resolved
Hide resolved
As discussed with @timuthy I will adapt the PR so that it's allowed to specify both the non-regional and regional fields (e.g., |
b817f16
to
23e6f22
Compare
23e6f22
to
671c536
Compare
Looks good to me. |
671c536
to
fe3b5eb
Compare
Thanks, merging after rebase. |
What this PR does / why we need it:
Allow
region
-ized fields in OpenStackCloudProfileConfig
. Some OpenStack environments have dedicated keystone URLs, floating pools or load balancer per region/data center. Today, you would have to create a dedicatedCloudProfile
per region (although the backing cloud provider is the same). That's unfortunate. With this PR, it's possible to configure regions for the mentioned properties. This will allow to have only oneCloudProfile
like for the hyperscalers.Special notes for your reviewer:
KeystoneURL
fromstring
to*string
(because it's optional now) to prevent vendoring issues. We could do that later if we want.Release note: